Subject: appnLocalTgPortName

From: "R.E. (Robert) Moore (254-4436)" <[email-masked]>
Date: Mon, 23 Oct 95 08:47:01 EDT

This object should not be part of the appnLocalTgTable, since its value
is not known to TRS.  Even though implementations are not required to
match the APPN node structure, we have found that it is a good guide to
how most implementations are actually done.  Placing this object in
this table, where all of the other objects are TRS-supplied, will mean
that information must be retrieved from two components when a
Management Station retrieves a row of the table.  This greatly
increases the chance of a timeout before the data can be returned.

This object should be removed from the appnLocalTgTable.

---

From: Bob Clouston <[email-masked]>
Date: Mon, 23 Oct 95 20:39:34 EDT

This object associates a local connection network definition with a port.
How do you intend to convey this information in the MIB?

I agree that limiting a table to information from one component is a good
goal.  However, this is not the first table that draws information from two
components.  For example, I believe that the link station table gets 
information from both CS and DLCx.  

Bob Clouston
Cisco Systems